View UM0932_8881178.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

october 2013 docid17385 rev 3 1/43 UM0932 user manual st7580 - fsk, psk multi-mo de power line networking system-on-chip introduction this user manual, which targets application developers, provides complete information on how to use the st7580 device in applications by describing the embedded functions and protocol layers, with a focus on the commands and parameters available to the user to control and operate the device through its host interface. for ordering information, mechanical and electr ical device characterist ics, please refer to the st7580 datasheet available from www.st.com. www.st.com
contents UM0932 2/43 docid17385 rev 3 contents 1 documentation conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 list of abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2 functional overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.1 protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.2 st7580 power line frames: structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.3 power line data transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 2.4 power line data reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 st7580 reception flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 3 host interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 3.1 uart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 3.2 communication protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 3.2.1 frame types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 3.2.2 local frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 3.2.3 acknowledgment messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 3.2.4 status message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 3.2.5 local port arbitration rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.2.6 frame delimitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.2.7 data communication from the st7580 to the external host . . . . . . . . . . 17 3.2.8 data communication from external host to the st7580 . . . . . . . . . . . . . 18 3.2.9 host interface timeouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3.3 command codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3.3.1 bio_resetrequest (3ch) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.3.2 bio_resetconfirm (3dh) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.3.3 bio_resetindication (3eh) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3.3.4 mib_writerequest (08h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3.3.5 mib_writeconfirm (09h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 3.3.6 mib_readrequest (0ch) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 3.3.7 mib_readconfirm (0dh) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 3.3.8 mib_eraserequest (10h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 3.3.9 mib_eraseconfirm (11h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 3.3.10 pingrequest (2ch) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 3.3.11 pingconfirm (2dh) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
docid17385 rev 3 3/43 UM0932 contents 43 3.3.12 phy_datarequest (24h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 3.3.13 phy_dataconfirm (25h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 3.3.14 phy_dataindication (26h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 3.3.15 dl_datarequest (50h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 3.3.16 dl_dataconfirm (51h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 3.3.17 dl_dataindication (52h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 3.3.18 dl_snifferindication (5ah) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 3.3.19 ss_datarequest (54h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 3.3.20 ss_dataconfirm (55h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 3.3.21 ss_dataindication (56h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 3.3.22 ss_snifferindication (5eh) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 3.3.23 cmd_syntaxerror (36h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 4 management information base (mib) . . . . . . . . . . . . . . . . . . . . . . . . . . 34 4.1 mib table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 4.2 mib parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 4.2.1 00h (modem configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 4.2.2 01h (phy layer configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 4.2.3 02h (ss key) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 4.2.4 04h (last data indication) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 4.2.5 05h (last tx confirm) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 4.2.6 06h (phy data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 4.2.7 07h (dl data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 4.2.8 08h (ss data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 4.2.9 09h (host interface timeout) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 4.2.10 0ah (firmware version) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 5 reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 6 revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
list of tables UM0932 4/43 docid17385 rev 3 list of tables table 1. list of abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 table 2. phy frame description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 table 3. dl frame description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 table 4. ss frame description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 table 5. uart baud rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 table 6. local frame format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 table 7. ack and nak messages codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 table 8. status message composition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 table 9. communication protocol timeouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 9 table 10. request command codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 table 11. confirm command codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 table 12. error command codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 table 13. error commands: syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 table 14. error commands: errordata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 table 15. indication command codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 table 16. bio_resetrequest: syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 table 17. bio_resetconfirm: syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 table 18. bio_resetindication: syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 table 19. bio_resetindication: resetdata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 table 20. mib_writerequest: syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 table 21. mib_writerequest: requestdata. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 3 table 22. mib_writeconfirm: syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 table 23. mib_readrequest: syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 table 24. mib_readrequest: requestdata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 table 25. mib_readconfirm: syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 table 26. mib_readconfirm: confirmdata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 4 table 27. mib_eraserequest: syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 table 28. mib_writerequest: requestdata. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 4 table 29. mib_eraseconfirm: syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 table 30. pingrequest: syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 table 31. pingrequest: requestdata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 table 32. pingconfirm: syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 table 33. pingconfirm: confirmdata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 table 34. phy_datarequest: syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 table 35. phy_datarequest: requestdata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 table 36. phy_dataconfirm: syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 table 37. phy_dataconfirm: confirmdata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 7 table 38. phy_dataindication: syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 table 39. phy_dataindication: indicationdata. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 table 40. dl_datarequest: syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 table 41. dl_dataconfirm: syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 table 42. dl_dataindication: syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 table 43. dl_snifferindication: syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 table 44. ss_datarequest: syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 table 45. ss_datarequest: requestdata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1 table 46. ss_dataconfirm: syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 table 47. ss_dataindication: syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 table 48. ss_dataindication: indicationdata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
docid17385 rev 3 5/43 UM0932 list of tables 43 table 49. ss_snifferindication: syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 table 50. cmd_syntaxerror: syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 table 51. cmd_syntaxerror:errordata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 table 52. management information base (mib) objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 table 53. mib object 00h: mib_writerequest and mib_ readrequest data format . . . . . . . . . . . . . 35 table 54. mib object 01h: mib_writerequest and mib_ readrequest data format . . . . . . . . . . . . . 35 table 55. mib object 02h: mib_writerequest and mib_ readrequest data format . . . . . . . . . . . . . 40 table 56. mib object 04h: mib_writerequest and mib_ readrequest data format . . . . . . . . . . . . . 41 table 57. mib object 05h: mib_writerequest and mib_ readrequest data format . . . . . . . . . . . . . 42 table 58. mib object 06h: mib_writerequest and mib_ readrequest data format . . . . . . . . . . . . . 43 table 59. mib object 07h: mib_writerequest and mib_ readrequest data format . . . . . . . . . . . . . 43 table 60. mib object 08h: mib_writerequest and mib_ readrequest data format . . . . . . . . . . . . . 44 table 61. mib object 09h: mib_writerequest and mib_ readrequest data format . . . . . . . . . . . . . 44 table 62. mib object 0ah: mib_writerequest and mib_ readrequest data format . . . . . . . . . . . . . 44 table 63. document revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
list of figures UM0932 6/43 docid17385 rev 3 list of figures figure 1. functional overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 figure 2. physical frame structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 figure 3. data link frame structur e. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 figure 4. security services frame structur e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 figure 5. st7580 reception flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 figure 6. st7580 and external host: uart connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 figure 7. local port character format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 figure 8. local frame format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 figure 9. timeout inter character tic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 figure 10. data flow from st7580 to the external host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 figure 11. data flow from external host to the st7580 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
docid17385 rev 3 7/43 UM0932 documentation conventions 43 1 documentation conventions list of abbreviations the following abbreviations are used: table 1. list of abbreviations abbreviation description mib management information base pga programmable gain amplifier zc zero-crossing phy physical layer dl data link layer crc cyclic redundancy check aes advanced encryption standard uart universal asynchronous receiver transmitter t ic inter character timeout t ack acknowledge timeout t sr service request timeout ss security services bio basic input output hi host interface
functional overview UM0932 8/43 docid17385 rev 3 2 functional overview the st7580 device provides to the external ho st a complete physical layer (phy) and some data link layer (dl) services for power line communication. it is mainly developed for smart metering applications in cenelec a band, but suitable also for othe r control applications and remote load management in cenelec b band. a uart host interface is available for communi cation with an external host, exporting all the functions and services required to configure and control the device and its protocol stack. 2.1 protocol stack below is a list of the protocol layers and functions embedded in the st7580: ? physical (phy) layer: hosted in the phy processor, implements two different modulation schemes for communication through power line: a b-fsk modulation up to 9.6 kbps and a mult i-mode psk modulation with channel quality estimation, dual channel receiving mode and convolutional coding, delivering a throughput up to 28.8 kbps. ? data link (dl) layer: the embedded dl layer hosted in the protocol controller offers framing and error correction services. a furt her security service (ss) based on 128-bit aes algorithm is also available fo r crypting / decrypting frames. ? management information base (mib): an information database with the data required for proper configuration of the system. ? host interface: all of the services of the ph y, dl and mib are exported to an external host through the local uart port. figure 1. functional overview $0y 3+</d\hu +267,qwhuidfh 3+< 3urfhvvru 3urwrfro &rqwuroohu '//d\hu 0,% /rfdo3ruw 8$57 7;' 5;' 7b5(4 %5 %5 0,% ([whuqdo +267 $qdorj)urqw(qg 3rzhuolqh&rppxqlfdwlrq 67
docid17385 rev 3 9/43 UM0932 functional overview 43 2.2 st7580 power lin e frames: structure the st7580 device can be configured by the external host to transmit and receive frames over the power line in accordance wit h three different frames structures: 1. physical (phy) frames, built with some di fferences between psk and fsk modulations (see [ ] ), as represented in figure 2 : figure 2. physical frame structure table 2 lists the fields of phy frame. 2. data link (dl) frames, adding crc field to physical sdu. figure 3 shows the frame structure: figure 3. data link frame structure the external host is allowed to choose the crc algorithm used (length, endianness, fields involved in calculation) through a dedicated mib object (modem configuration 00h, section 4.2.1 ). the length field is automatically handled by st 7580 and its value is by default equal to the length of payload and crc fields. table 2. phy frame description field name length description and values length 1 payload length. allowable values: from 0 up to 255 payload length data bytes $0y 3uhdpeoh 35( 8qltxh:rug 8: 3d\ordg iurpxswre\whv e\whv iurpxswre\whv 3+<6'8 36. 0r gh e\wh /hqjwk e\wh $0y 3d\ordg iurpxswre\whv 3+<6'8 /hqjwk e\wh &5& rue\wh '/6'8
functional overview UM0932 10/43 docid17385 rev 3 table 3 lists the fields of dl frame. 3. security services (ss) frames, providing authentication to payload using cryptographic algorithms based on aes with 128-bit keys. authentication is provided appending to user data an aes-cmac digest. a dedicated key (stored in the mib object ss key 02h, section 4.2.3 ) is used for both transmitting and receiving frames. figure 4 shows the ss frame structure. figure 4. security services frame structure table 4 lists the fields of ss frame. table 3. dl frame description field name length description and values dl length 1 total length of payload and crc fields. payload dl length ? length of crc data bytes crc 1, 2 or 4 crc calculated in accordance with algorithm chosen in dedicated mib object (modem configuration 00h, section 4.2.1 ). table 4. ss frame description field name length description and values header hl part of user data transmitted in clear. encrypted payload len-29-hl part of user data transmitted ciphered. iv 12 initialization vector of aes-ctr algorithm. hl 1 header field length. digest 16 aes-cmac digest computed on header , encrypted payload, iv and hl fields. $0y +hdghu iurpxswre\whv 3+<6'8 /hqjwk e\wh &5& rue\wh '/6'8 (qfu\swhg 3d\ordg ,qlwldol]dwlrq 9hfwru,9 'ljhvw +hdghu /hqjwk +/ e\wh e\whv e\whv +/e\whv iurpxswre\whv 666'8
docid17385 rev 3 11/43 UM0932 functional overview 43 2.3 power line data transmission in order to manage data transmission to the po wer line, three different dedicated services are available to the external host. 1. phy_data transmission, with frames structured as in figure 2 , requiring the payload as the only external parameter and building automatically the length field. 2. dl_data transmission, with frames structured as in figure 3 , requiring the payload as the only external parameter and building automatically the l ength and crc fields. 3. ss_data transmission, with frames structured as in figure 4 , requiring the payload and header length (greater than 3) as extern al parameters, buildin g automatically the length, crc and hl field, deciding an arbitrary initialization vector and encrypting the payload. the external host is allowed to access the st7580 device and choose which among the three frame structures are utilized for transmitting data over the power line by selecting the corresponding available service. 2.4 power line data reception in order to manage data reception from the power line, the st7580 can be configured to be able to receive in accordance with only one frame structure. the external host is allowed to set, through a dedicated mib object (modem configuration, 00h section 4.2.1 ), the only frame structure the st7580 is able to receive. the st7580 embeds three corresponding available services: 1. phy_data indication: generated as soon as a frame in compliance with phy frame structure ( figure 2 ) has been received, it exports the phy payload field 2. dl_data indication: generated as soon as a frame in compliance with dl frame structure ( figure 3 ) has been received, it exports the dl payload field 3. ss_data indication: generated as soon as a frame in compliance with ss frame structure ( figure 4 ) has been received, it exports the ss payload field. a further feature of st7580 configuration is the sniffer flag. it can be activated by the external host through a dedicated mib object (modem configuration, 00h section 4.2.1 ) and it makes two further services available: 1. dl_sniffer indication: generated as soon as a frame in compliance with dl frame structure ( figure 3 ) with a wrong crc has been received, it exports both dl payload and wrong crc fields. 2. ss_sniffer indication: generated as soon as a frame in compliance with ss frame structure ( figure 4 ) that couldn't be correctly decr ypted or authenticated has been received, it exports the whole ss_sdu field.
functional overview UM0932 12/43 docid17385 rev 3 st7580 reception flow the reception flow for incoming frames is depicted in figure 5 : figure 5. st7580 reception flow $0y 1r,qglfdwlrq 66b6qliihu,qglfdwlrq 3d \ ordg &5& 5l j kw <hv 1r :urqj 5ljkw 1r <hv 3+<+hdghu3uhdpeoh8:0rghuhfhswlrq /hqjwk)lhog / uhfhswlrq 3d\ordguhfhswlrqxswr/%\whv 5hfhlylqj0rgh 3+<iudphv 3+<b'dwd,qglfdwlrq 3d \ ordg &rpsxwh&5& &5&&khfn '/b'dwd,qglfdwlrq 3d \ ordg 6qliihu (qdeohg 1r,qglfdwlrq '/b6qliihu,qglfdwlrq 3d \ ordg &5& <hv 1r 66iudphv 5hfhlylqj0rgh '/ iudphv :urq j 66ghfu\swlrqdqg dxwkhqwlfdwlrq 66b'dwd,qglfdwlrq 3d \ ordg <hv 1r 6qliihu (qdeohg
docid17385 rev 3 13/43 UM0932 host interface 43 3 host interface the host interface is a communication port used by the external host to exchange data with the st7580 device. the host interface consists of a local port (a standard uart), a communication protocol and a set of commands exchanged between st7580 and the external host. it manages the communication and arbitration on the local port, and provides access to st7580 internal services. 3.1 uart the local communication is a half duplex asynchronous serial link (uart) using a receiving input (rxd), a transmitting output (txd) and a t_req signal to manage the communication. the connection diagram of the st7580 using uart as host interface port is shown in figure 5 . figure 6. st7580 and external host: uart connections the communication baud rate is selected afte r the st7580 reset, in accordance with the status of local input ports br0, br1 listed in table 5 : table 5. uart baud rate br1 br0 baudrate (b/s) 0 0 9600 0 1 19200 1 0 38400 1 1 57600 $0y ([whuqdo+267 8$57 /rfdo3ruw 7;' 5;' 7b5(4 %5 %5 ([whuqdo8$57 %dxgudwh vhohfwlrq 67
host interface UM0932 14/43 docid17385 rev 3 the uart interface has two data channels: ? txd carries data from the st7580 to the host ? rxd carries data from the host to the st7580 a local request input signal is implemented on the t_req pin. st7580 uart is a half duplex asynchronous serial port without hardware control flow. uart settings used are: ? half duplex mode ? standard nrz bit coding ? lsbit first transmission: the bits withi n each byte are sent lsbit to msbit ? the exchanged frames are composed of characters ? a single character is composed of 1 start bit, 8 data bits and 1 stop bit ? 0-5 v or 0-3.3 v levels on txd, rxd, t_req signals. figure 7 shows the character format: figure 7. local po rt character format 3.2 communication protocol the host interface process implemented in the st7580 device performs the following tasks: ? the frame format definition ? the reception mechanism: the uart stan dard on half duplex data channel is implemented and collisions are avoided ? the acknowledgement to received frames ? the timeout management ? the error checking: length, syntax and checksum field of a received frame are controlled and a repetition is requested in case of error. 3.2.1 frame types a frame is a sequence of one or more characters encapsulating a data exchanged between the st7580 device and the host controller. the communication protocol defines several frame formats for the different steps of the communication protocol (access to st7580 services, acknowledgement, device status). $0y ' ' ' ' ' ' ' ' % 6 0 % 6 / 6wduw %lw 6wrs %lw ,'/(vwdwh pdun w elw w elw gdwdelwv fkdudfwhu
docid17385 rev 3 15/43 UM0932 host interface 43 all the st7580 resources and services (phy layer, dl layer and mib management) are available through local commands and they can be handled by the external host using the local communication serial interface and the commands defined in the following paragraphs. 3.2.2 local frame the format of the frame used in the local communication between the st7580 and the external host is graphically represented in figure 8 : figure 8. local frame format the frame fields are described in table 6 : byte endianness for fields (data and checksum) with a length greater than one byte is: ? data field: structured in sub-fields in a ccordance with comman d code specifications described in section 3.3 . ? checksum field: it is sent lsbyte first. 3.2.3 acknowledgment messages after receiving a local frame on the host interface, both external host and the st7580 must send, through either txd (st7580) or rxd (external host), an acknowledgement or not acknowledgement message. the two messages have the same format for both st7580 and external host and they are 1-byte long. table 6. local frame format field byte length value description stx 1 02h or 03h start of text delimiter length 1 0 ? 255 byte length of data field command code 1 0 ? ffh command code data 0 ? 255 data field (255 byte max.) checksum 2 the checksum of the local frame is the result of the addition of the elemen ts of the frame, from length up to the last data byte, or up to the command byte if there is no data byte. $0y 67; /hqjwk &rppdqg &rgh '$7$ &khfnvxp
host interface UM0932 16/43 docid17385 rev 3 table 7 lists their fixed codes. 3.2.4 status message the status message is a frame sent by the st7580 to the host controller when the t_req signal is pulled down. it is composed of 2 bytes filled in accordance with st7580 stat us and configurat ion. the first byte (byte index 0) is always the character ??? (ascii code 3fh). other bytes are set as in table 8 : table 7. ack and nak messages codes symbol definition code ack acknowledgement 06h nak not acknowledgement 15h table 8. status message composition byte index bit index description available values 0 status message first byte 3fh 1 0 configuration status 0: autoreconfiguratio n correctly occurred 1: autoreconfiguration occurred with errors or at least one among mib objects 00h (modem config), 01h (phy config), 02h (ss key) hasn?t changed its default value after boot 1 transmission status 0: the st7580 is not transmitting a power line frame 1: the st7580 is transmitting a power line frame 2 reception status 0: the st7580 is not receiving a power line frame 1: the st7580 is receiving a power line frame 3-4 active layer 0: phy layer 1: dl layer 2: ss layer 3: st7580 not configured 5 overcurrent flag 0: no overcurrent event on last transmission 1: last transmission generated at least one overcurrent event 6-7 estimated st7580 temperature 0: t < 70 c (typical) 1: 70 c < t <100 c (typical) 2: 100 c < t < 125 c (typical) 3: t > 125 c (typical)
docid17385 rev 3 17/43 UM0932 host interface 43 3.2.5 local port arbitration rules the st7580 modem is always the communication master. in case of no local transfer, the st7580 can initiate a local co mmunication without taking into account the external host status. on the other hand, when the external ho st wants to send a local frame, it must first send a request through the t_req (transmitting request) input port. then the st7580 answers with a status message allowing or not the reception of a frame (or any other command). 3.2.6 frame delimitation data coming from the uart serial port are an as ynchronous flow of bytes. in order to divide the bytes flow into a frames flow, the st75 80 communication protocol uses two methods: length and timeout. when the number of bytes received reaches t he expected frame length, in accordance with the frame type's characteristi cs, the frame reception ends. the time interval between two consecutive characters (two local frames including start and stop bits) in a local frame must not exceed t ic (timeout inter-characte r): the receiving part (st7580 host interface or external host) no longer accepts any character after this delay expiration. figure 9. timeout inter character t ic the timeout inter character (t ic ) is set by default at 10 ms after a reset and it can be modified by writing a dedicated mib object (host interface timeout 09h, section 4.2.9 ). if the length and the checksum are both correct, the received frame is accepted, otherwise all previous characters are discarded. 3.2.7 data communication from th e st7580 to the external host when the st7580 needs to transmit a frame to the host, it can directly send it without any previous request. the local frame is automati cally built with an stx value equal to 02h. if the length and the checksum of the local frame are both correct, the external host acknowledges with an ack character. in ot her cases, it answers with a nak character. if one of the following cases is verified on the rxd line: ? negative acknowledgement (nak) ? any other frame ? no frame within t ack interval. $0y &kdudfwhu &kdudfwhu 7 ,&
host interface UM0932 18/43 docid17385 rev 3 the st7580 device repeats the frame only once after a delay corresponding to t ack , changing the stx value to 03h. acknowledgem ent to re-transmitted fr ames is considered positive by default, even if the host controller answers with a negative acknowledgement. figure 10. data flow from st7580 to the external host 3.2.8 data communication from external host to the st7580 when the external host needs to initiate a da ta transfer to the st7580, it must set the t_req signal at low level. as soon as the st 7580 is not busy, it answers with the status message confirming or not th e data channel availability. if the communication is possible, the external host can start sending a local frame (built with stx field equal to 02h) within the t sr delay. the t_req signal is set to high logic value as soon as the stx field of the local frame (see section 3.2.2 ) has been sent. if the first byte of the local frame is not received before the t sr delay, the st7580 ignores it. figure 11. data flow from external host to the st7580 at the end of the data reception on the rxd line, the st7580 sends an acknowledgement message on the txd line to inform about the stat us of the transmission (ack or nak) within a t ack interval. if the length and the checksum of the local frame are both correct, the st7580 acknowledges with an ack character. in ot her cases, it answers with a nak character. in case of a nak response or no acknowledgement from the st7580 within the t ack time-out, a complete sequence must be restarted to repeat the communication. $0y 7b5(4 1$ . 5;' 7;' $& . /rfdo)udph iurp67 7 $&. 7 $&. /rfdo)udph iurp67 $0y 7b5(4 /rfdo)udph 6wdwxv $&. 5;' 7;' 7 65 7 $&.
docid17385 rev 3 19/43 UM0932 host interface 43 3.2.9 host interface timeouts all the default values of host in terface timeouts are reported in table 9 . 3.3 command codes each command frame exchanged between the external host and the st7580 carries a command, identified by a unique command code (declared in the command code field as in figure 8 :) it is possible to distinguish four different command types: ? request commands sent by the external host to use a st7580 service ? confirm commands sent by the st7580 to answer a previous request command correctly executed ? error commands sent by the st7580 to answer a previous request command not executed ? indication commands sent by the st7580 to inform the external host about a change on its services; these are unsolicited commands not following any request. request commands request commands are sent by the external ho st to perform an action on st7580. st7580 executes the command and answers the external host through either a confirm command or an error command. table 10 shows all request commands: their syntax a nd data fields are explained in the next paragraphs. table 9. communication protocol timeouts timeout default value [ms] t ic 10 t ack 40 t sr 200 table 10. request command codes group request command code reset bio_resetrequest ( section 3.3.1 )3ch mib mib_writerequest ( section 3.3.4 )08h mib_readrequest ( section 3.3.6 )0ch mib_eraserequest ( section 3.3.8 )10h ping pingrequest ( section 3.3.10 )2ch data phy_datarequest ( section 3.3.12 )24h dl_datarequest ( section 3.3.15 )50h ss_datarequest ( section 3.3.19 )54h
host interface UM0932 20/43 docid17385 rev 3 confirm commands confirm commands are sent by the st7580 to t he external host after a previous request command, if the request itself has been correctly executed. table 11 lists confirm command codes: their syntax and data fields are explained in the next paragraphs. error commands error commands are sent by the st7580 to th e external host after a previous request command, if it has not been executed or if an error has occurred while it was executing. the data field of the correspondent local frames presents a same syntax for all error command codes, with the exception of cmd_syntaxerror ( section 3.3.23 ). it is composed of 1 byte and it is coded in ac cordance with the values listed in table 14 . table 11. confirm command codes group confirm command code reset bio_resetconfirm ( section 3.3.2 )3dh mib mib_writeconfirm ( section 3.3.5 )09h mib_readconfirm ( section 3.3.7 )0dh mib_eraseconfirm ( section 3.3.9 )11h ping pingconfirm ( section 3.3.11 )2dh data phy_dataconfirm ( section 3.3.13 )25h dl_dataconfirm ( section 3.3.16 )51h ss_dataconfirm ( section 3.3.20 )55h table 12. error command codes group error command code reset bio_reseterror 3fh mib mib_writeerror 0bh mib_readerror 0fh mib_eraseerror 13h data phy_dataerror 27h dl_dataerror 53h ss_dataerror 57h syntax error cmd_syntaxerror 36h table 13. error commands: syntax source command (args) possible response st7580 commanderror (errordata) ---
docid17385 rev 3 21/43 UM0932 host interface 43 indication commands indication commands are sent by the st7580 to th e external host. they notify a reset event or a power line data reception. table 15 lists all the indication commands: their syntax and data fields are explained in the next paragraphs. 3.3.1 bio_resetrequest (3ch) this command is used by the external host to force software reset in the st7580. 3.3.2 bio_resetconfirm (3dh) this command is sent by the st7580 after the correct reception of a bio_resetrequest ( section 3.3.1 ) command. the confirmdata field is always composed of 1 byte equal to 00h. table 14. error commands: errordata error cause value description wrong parameter length (wpl) 02h data field length in the previous request was wrong wrong parameter value (wpv) 03h at least one of the parameters values in the previous request was invalid. busy 04h system busy, operation couldn?t be performed. thermal error 0bh device internal temperature within threshold 4 [ section 5 ], st7580 refused to transmit. general error ffh generic error code. table 15. indication command codes group command code reset bio_resetindication ( section 3.3.3 )3eh data phy_dataindication ( section 3.3.14 ) 26h dl_dataindication ( section 3.3.17 ) 52h dl_snifferindication ( section 3.3.18 )5ah ss_dataindication ( section 3.3.21 ) 56h ss_snifferindication ( section 3.3.22 )5eh table 16. bio_resetrequest: syntax source command(args) possible response ext. host cmd_resetrequ est() bio_resetconfirm table 17. bio_resetconfirm: syntax source command(args) possible response st7580 bio_resetconfirm(confirmdata) ---
host interface UM0932 22/43 docid17385 rev 3 3.3.3 bio_resetindication (3eh) this command is sent by the st7580 to notify the host about a reset or a power-on event. 3.3.4 mib_writerequest (08h) this command is used by the external host to access an object of the mib. the st7580 checks the parameters for validation: ? if the check is valid, the object is updated in the database and the st7580 replies with a mib_writeconfirm ( section 3.3.5 ). ? if the check is not valid, the request is rejected and the st7580 replies with a mib_writeerror ( table 12 ). table 18. bio_resetindication: syntax source command(args) possible response st7580 bio_resetindication(resetdata) --- table 19. bio_resetindication: resetdata byte index bit index label description 0 0 - 1 reset cause 0: resetn pin at low state (hardware reset) or power-on 1: watchdog 2: bio_resetrequest (see section 3.3.1 ) command 2 autoreconfiguration error 0: autoreconfiguratio n correctly occurred 1: autoreconfiguration occurred with errors or at least one among mib objects 00h (modem config), 01h (p hy config), 02h (ss key) hasn't changed its default value after power-on 3 autoreconfiguration: modem config object error 0: autoreconfiguration on mib ob ject 00h (modem config) correctly occurred, if such an object has been written by host through mib_writerequest command after power-on 1: errors during autoreconfiguratio n on mib object 00h (modem config) or the object hasn't been changed its default value after power-on 4 autoreconfiguration: phy config object error 0: autoreconfiguration on mib object 01h (phy config) correctly occurred, if such an object has been written by host through mib_writerequest command after power-on 1: errors during autoreconfiguration on mib object 01h (phy config) or the object hasn't been changed its default value after power-on 5 autoreconfiguration: ss keyobject error 0:autoreconfiguration on mib object 02h (ss key) correctly occurred, if such an object has been written by host through mib_writerequest command after power-on 1: errors during autoreconfiguration on mib object 02h (ss key) or the object hasn't been changed its default value after power-on 6 - 7 unused
docid17385 rev 3 23/43 UM0932 host interface 43 3.3.5 mib_writeconfirm (09h) this command is sent by the st7580 to acknowledge an mib_writerequest (see section 3.3.4 ), if the request has been acc epted and executed without errors. 3.3.6 mib_readrequest (0ch) this command is used by the external host to read the current value of an mib object. the st7580 checks the parameters for validation: ? if the check is valid, the object is updated in the database and the st7580 replies with a mib_readconfirm ( section 3.3.7 ). ? if the check is not valid, the request is rejected and the st7580 replies with a mib_readerror ( table 12 ). table 20. mib_writerequest: syntax source command(args) possible response source ext. host mib_writerequest (requestdata) request accepted: mib_writeconfirm request rejected: mib_writeerror (errordata) ext. host table 21. mib_writerequest: requestdata byte index label description 0index mib database entry index. refer to the mib table ( ta ble 5 2 ) for available objects allowed to be written. 1 ? n data data to be written in the mib location index. table 22. mib_writeconfirm: syntax source command(args) possible response st7580 mib_writeconfirm () none table 23. mib_readrequest: syntax source command(args) possible response ext. host mib_readrequest (requestdata) request accepted: mib_readconfirm (confirmdata) request rejected: mib_ readerror (errordata) table 24. mib_readrequest: requestdata byte index label description 0 index mib database entry index. refer to the mib table ( table 52 ) for available objects.
host interface UM0932 24/43 docid17385 rev 3 3.3.7 mib_readconfirm (0dh) this command is sent by the st7580 to acknowledge an mib_readrequest (see section 3.3.6 ) if the request has been accepted and executed without errors. 3.3.8 mib_eraserequest (10h) this command is used by the external host to erase the value of an mib object and set it to 0. this command is valid for erasable mib objects only ( table 52 ). the st7580 checks the parameters for validation: ? if the check is valid, the object is updated to a value equal to 0 in the database and the st7580 replies with an mib_eraseconfirm ( section 3.3.9 ). ? if the check is not valid, the request is rejected and the st7580 replies with an mib_eraseerror ( table 12 ). 3.3.9 mib_eraseconfirm (11h) this command is sent by the st7580 to acknowledge an mib_eraserequest (see section 3.3.8 ) if the request has been accepted and executed without errors. table 25. mib_readconfirm: syntax source command(args) possible response st7580 mib_readconfi rm(confirmdata) none table 26. mib_readco nfirm: confirmdata byte index label description 1 ? ndata current value of the mib object wit h index expressed in the previous mib_readrequest command ( section 3.3.6 ). table 27. mib_eraserequest: syntax source command(args) possible response ext. host mib_eraserequest(requestdata) request accepted: mib_eraseconfirm request rejected: mib_eraseerror (errordata) table 28. mib_writerequest: requestdata byte index label description 0 index mib database entry index. refer to the mib table ( table 52 ) for available objects. table 29. mib_eraseconfirm: syntax source command(args) possible response st7580 mib_eraseconfirm () none
docid17385 rev 3 25/43 UM0932 host interface 43 3.3.10 pingrequest (2ch) this command is sent by external host to test the robustness of the local port link with the st7580. if accepted, the st7580 answers with a pingconfirm command ( section 3.3.11 ). 3.3.11 pingconfirm (2dh) this command is sent by the st7580 to notify the reception of a pingrequest. the payload field of the local frame presents the same data received in the previous pingrequest. 3.3.12 phy_datarequest (24h) this command is sent by the external host to request data transmission and it exports the phy_data transmission service ( section 2.3 ). ? if accepted, the st7580 constructs a phy frame ( figure 2 ) that is transmitted over the power line in accordance with the details expressed in requestdata field ( table 35 ). a positive phy_dataconfirm ( section 3.3.13 ) is generated at the end of the transmission. ? if refused, the modem generates a phy_dataerror ( table 12 ). table 30. pingrequest: syntax source command(args) possible response external host pingrequest(requestdata) request accepted: pingconfirm (confirmdata) table 31. pingrequest: requestdata byte index label description 0 - n data payload with variable length table 32. pingconfirm: syntax source command(args) possible response st7580 pingconfirm(confirmdata) -- table 33. pingconfirm: confirmdata byte index label description 0 - n data payload with the values received in the previous pingrequest ( section 3.3.10 ) table 34. phy_datarequest: syntax source command(args) possible response external host phy_datarequest( requestdata) request accepted: phy_dataconfirm (confirmdata) request rejected: phy_ dataerror (errordata)
host interface UM0932 26/43 docid17385 rev 3 table 35. phy_datarequest: requestdata byte index bit index label description and available values 0 0 custom / mib frequency selection of frequency to use between mib and custom frequency 0: tx frequency is the high or low frequency as in phy_config ( table 54 ) mib object 1: tx frequency is specified in bytes [1 ? 3] (tx frequency) 1 frequency overwrite selection of phy_config mib object overwrite ( ta ble 5 4 ). this field is taken into account if t he custom / mib frequency? bit is equal to ?1? only. 0: tx frequency expressed in the following bytes (1 ? 3) won't overwrite the frequency in phy_config ( ta ble 54 ) mib object 1: tx frequency expressed in the following bytes (1 ? 3) overwrites frequency in phy_config ( ta ble 54 ) mib object 2 frequency set selection of frequency in phy_config mib object 0: tx frequency is the lowfrequency in phy_config mib object 1: tx frequency is the highfrequency in phy_config mib object 3 gain selector selection of tx gain for frame transmission 0: tx gain set as in phy config mib object (tx gain parameter ( table 54 )) 1: tx gain is specified in the following tx gain byte (2 or 4) 4-6 frame modulation modulation of the frame to be transmitted 0: b-psk 1: q-psk 2: 8-psk 3: b-fsk 4: b-psk coded 5: q-psk coded 6: reserved 7: b-psk coded with peak noise avoidance 7 zero crossing synchronization 0: transmission frame starts on any instant 1: transmission frame start after zc delay value defined in phy config mib object ( table 54 ) 1 - 3 tx frequency frequency value (in hz) that the output signal is modulated around, to be expressed if ?custom / mib frequency? bit is equal to ?1? only. 4 (or 1) 0 ? 4 tx gain tx gain [ ] to be expressed if gain selector bit is equal to ?1? only. 5 ? 7 unused 5 ? 254 (or 1 ? 254, 2 ? 254, 4 ? 254) payload payload to be sent (up to 254 bytes)
docid17385 rev 3 27/43 UM0932 host interface 43 3.3.13 phy_dataconfirm (25h) this command is sent by the st7580 to provide a positive confirmation to a phy_datarequest (see section 3.3.12 ) previously requested by the external host. table 36. phy_dataconfirm: syntax source command(args) possible response st7580 phy_dataconfirm (confirmdata) none table 37. phy_dataconfirm: confirmdata byte index bit index label description 0 0 ? 1 max. temp. max temperature reached dur ing phy frame transmission. 0: t < 70 c (typical) 1: 70 c < t < 100 c (typical) 2: 100 c < t < 125 c (typical) 3: t > 125 c (typical) 2 ? 6 max. gain if current control feature (mib object phy config 01h, section 4.2.2 ) is active, max. gain used during last transm ission. if current control feature is not active, gain used during last transmission. 7 unused 1 0 ? 1 min. temp min. temperature reached dur ing phy frame transmission. 0: t < 70 c (typical) 1: 70 c < t < 100 c (typical) 2: 100 c < t < 125 c (typical) 3: t > 125 c (typical) 2 ? 6 min. gain if current control feature (mib object phy config 01h, section 4.2.2 ) is active, min. gain used during last tran smission. if current control feature is not active, gain used during last transmission. 7 unused 2 0 ? 6 overcurrent events number number of overcurrent events reached during phy frame transmission. valid if the current contro l feature is active only. 7 overcurrent notification notification about the overcurrent reac hed during last transmission. valid whether the current control is active or not. 0: max. output current [ ] value not reached 1: max. output current [ ] value reached 3 - 4 zc delay delay between the last transmitted uw last bit and the mains zero- crossing (signed value), expressed in 13 s step.
host interface UM0932 28/43 docid17385 rev 3 3.3.14 phy_dataindication (26h) this command is sent by the st7580 device after a reception of a power line frame in compliance with phy frame specification ( figure 3 ) and it exports the phy_data indication service ( section 2.4 ). the command notification occurs if the mode m is set at phy layer only at mib object modem config 00h ( section 4.2.1 ), as in the diagram flow in figure 5 . 3.3.15 dl_datarequest (50h) this command is sent by the external host to request data transmission and it exports the dl_data transmission service ( section 2.3 ). ? if accepted, the st7580 constructs a dl frame ( figure 3 ) that is transmitted over the power line according to the details expresse d in requestdata field (same format as phy_datarequest, table 35 ) and with automatically appended crc field with the format selected in mib ob ject modem config (00h, section 4.2.1 ). a positive dl_dataconfirm ( section 3.3.16 ) is generated at the end of the transmission ? if refused, the modem generates a dl_dataerror ( table 12 ). table 38. phy_dataindication: syntax source command(args) possible response st7580 phy_dataindication (indicationdata) none table 39. phy_dataindication: indicationdata byte index bit index label description and available values 0 0 - 2 frame modulation frame modulation on the last data ind ication received 0: b-psk 1: q-psk 2: 8-psk 3: b-fsk 4: b-psk coded 5: q-psk coded 6: reserved 7: b-psk coded with peak noise avoidance 3 rx channel rx channel on the last data indication received 0: low channel 1: high channel 4 - 7 pga value pga value on the last data indication received 1snr snr estimated over the unique word reception (signed value, valid for psk received frames only, equal to 255 ? no meaning ? for fsk received frames) 2 - 3 zc delay delay between the received uw last bit and the mains zero- crossing (signed value), expressed in 13 s step 4 - 254 phy payload received payload (up to 251 bytes)
docid17385 rev 3 29/43 UM0932 host interface 43 3.3.16 dl_dataconfirm (51h) this command is sent by the st7580 to provide a positive confirmation to a dl_datarequest ( section 3.3.15 ) previously requested by the external host. the confirmdata field has the same format as for phy_dataconfirm (see table 37 ). 3.3.17 dl_dataindication (52h) this command is sent by the st7580 after a reception of a power line frame in compliance with dl frame specification ( figure 3 , i.e. with a crc correct field) and it exports the dl_data indication service ( section 2.4 ). the command notification occurs if the modem is set for receiving dl or ss frames at mib object modem config 00h ( section 4.2.1 ), as in the diagram flow in figure 5 . the indicationdata fields are the same as for phy_dataindication ( table 39 ). 3.3.18 dl_snifferindication (5ah) this command is sent by the st7580 after a reception of a power line frame in compliance with dl frame specification ( figure 3 , i.e. with a wrong crc field) and it exports the dl_sniffer indication service ( section 2.4 ). the command notification occurs if the modem is set for receiving dl or ss frames at mib object modem config 00h ( section 4.2.1 ), as in the diagram flow in figure 5 . the indicationdata fields are the same as for phy_dataindication ( table 39 ). the payload field presents the wrong crc bytes also. table 40. dl_datarequest: syntax source command(args) possible response external host dl_datarequest(requestdata) request accepted: dl_dataconfirm (confirmdata) request rejected: dl_dataerror (errordata) table 41. dl_dataconfirm: syntax source command(args) possible response st7580 dl_dataconfirm (confirmdata) none table 42. dl_dataindication: syntax source command(args) possible response st7580 dl_dataindication (indicationdata) none table 43. dl_snifferindication: syntax source command(args) possible response st7580 dl_snifferindication (indicationdata) none
host interface UM0932 30/43 docid17385 rev 3 3.3.19 ss_datarequest (54h) this command is sent by the external host to request data transmission and it exports the ss_data transmission service ( section 2.3 ). ? if accepted, the st7580 constructs an ss frame ( figure 4 ) that is transmitted over the power line in accordance with the details expressed in requestdata field ( table 46 ). a positive ss_dataconfirm ( section 3.3.20 ) is generated at the end of the transmission. ? if refused, the modem generates an ss_dataerror ( table 12 ). table 44. ss_datarequest: syntax source command(args) possible response external host ss_datarequest(requestdata) request accepted: ss_dataconfirm (confirmdata) request rejected: ss_dataerror (errordata)
docid17385 rev 3 31/43 UM0932 host interface 43 ? if payload field is present, must be greater than or equal to 4 ? if payload field is not present, must be greater than or equal to 16. table 45. ss_datarequest: requestdata byte index bit index label description and available values 0 0 custom / mib frequency selection of frequency to use between mib and custom frequency 0: tx frequency is the high or low frequency as in phy_config ( section 4.2.2 ) mib object. 1: tx frequency is specified in bytes [1 ? 3] (tx frequency). 1 frequency overwrite selection of phy_config mib object overwrite ( section 4.2.2 ). this field is taken into account if the custom / mib frequency bit is equal to ?1? only. 0: tx frequency expressed in the follo wing bytes (1 ? 3) won't overwrite the frequency in phy_config ( section 4.2.2 ) mib object 1: tx frequency expressed in the following bytes (1 ? 3) overwrites frequency in phy_config ( section 4.2.2 ) mib object 2 frequency set selection of frequency in phy_config mib object 0: tx frequency is the lowfrequency in phy_config mib object 1: tx frequency is the highfrequency in phy_config mib object 3 gain selector selection of tx gain for frame transmission 0: tx gain set as in phy config mib object (tx gain parameter ( section 4.2.2 )). 1: tx gain is specified in the following tx gain byte (2 or 4). 4 ? 6 frame modulation modulation of the frame to be transmitted 0: b-psk 1: q-psk 2: 8-psk 3: b-fsk 4: b-psk coded 5: q-psk coded 6: reserved 7: b-psk coded with peak noise avoidance 7 zero crossing synchronizati on 0: transmission frame starts on any instant 1: transmission frame start after zc delay value defined in phy config mib object ( table 54 ) 1 - 3 tx frequency frequency value (in hz) that the output signal is modulated around, to be expressed if ?custom / mib frequency? bit is equal to ?1? only. 4 (or 1) 0 ? 4 tx gain tx gain to be expressed if gain selector bit is equal to ?1? only. 5 ? 7 unused 5 (or 2 or 4) header length length of header field. if payload is not empty, it must be : 4 = header length = payload length < 226). if payload is empty, it must be: 16 = header length < 226). 6 ? 231 (or 3 ? 228, 5 ? 230) header and payload header and payload to be sent (from 0 to 226 byte: header and payload to be sent as unique buffer).
host interface UM0932 32/43 docid17385 rev 3 3.3.20 ss_dataconfirm (55h) this command is sent by the st7580 to provide a positive confirmation to a ss_datarequest ( section 3.3.15 ) previously requested by the external host. the confirmdata field has the same format as for phy_dataconfirm (see table 37 ). 3.3.21 ss_datai ndication (56h) this command is sent by the st7580 after a reception of a power line frame in compliance with ss frame specification ( figure 4 , i.e. with a crc correct fi eld and encryp ted according to ss_key mib object, section 4.2.3 ) and it exports the ss_data indication service ( section 2.4 ). the command notification occurs if the modem is set for receiving ss frames at mib object modem config 00h ( section 4.2.1 ), as in the diagram flow in figure 5 . table 46. ss_dataconfirm: syntax source command(args) possible response st7580 ss_dataconfirm (confirmdata) none table 47. ss_dataindication: syntax source command(args) possible response st7580 ss_dataindication (indicationdata) none table 48. ss_dataindication: indicationdata byte index bit index label description and available values 0 0 ? 2 frame modulation frame modulation on the last dataindication received 0: b-psk 1: q-psk 2: 8-psk 3: b-fsk 4: b-psk coded 5: q-psk coded 6: reserved 7: b-psk coded with peak noise avoidance 3 rx channel rx channel on the last dataindication received 0: low channel 1: high channel 4 ? 7 pga value pga value on the last dataindication received 1snr snr estimated over the unique word re ception (signed value, valid for psk received frames only, equal to 255 ? no meaning ? for fsk received frames) 2 ? 3 zc delay delay between the received uw last bit and the mains zero-crossing (signed value), expressed in 13 s step 4 - 229 ss header and payload received header and payload (up to 226 bytes)
docid17385 rev 3 33/43 UM0932 host interface 43 3.3.22 ss_snifferindication (5eh) this command is sent by the st7580 after a re ception of a power line frame that couldn't be decrypted through the key value stored in the mib object ss_key 02h ( section 4.2.3 ) and it exports the ss_sniffer indication service ( section 2.4 ). the command notification occurs if the modem is set for receiving ss frames at mib object modem config 00h ( section 4.2.1 ), as in the diagram flow in figure 5 . the indicationdata fields are the same as for phy_dataindication ( table 39 ). the payload field won't present the wrong crc bytes. 3.3.23 cmd_syntaxerror (36h) this command is sent by the st758 to the external host after receiving a local frame with the value declared in command code not corresponding to any command listed in table 10 . table 49. ss_snifferindication: syntax source command(args) possible response st7580 ss_snifferindication (indicationdata) none table 50. cmd_syntaxerror: syntax source command(args) possible response st7580 cmd_syntaxerror(errordata) none table 51. cmd_syntaxerror:errordata byte index label description 0 error wrong command code declared in the pr evious local frame by external host
management information base (mib) UM0932 34/43 docid17385 rev 3 4 management information base (mib) the management information base collects all the parameters that allow the host to set and control the modem operation. as explained in section 3 , the mib objects can be directly accessed to update and read their values through dedicated commands ( section 3.3.4 , 3.3.63.3.6 , and 3.3.8 ). 4.1 mib table table 52 lists all the available mib objects, with t he related indexes, the default values and the allowed operation (read write). table 52. management information base (mib) objects index name factory default value length [byte] r/w/e 00h modem configuration 11h 1 r/w 01h phy configuration 014ff00119400e15000002359b58h 14 r/w 02h ss key 00000000000000000000000000000000h 16 r/w 03h reserved 00h 1 r 04h last data indication 00000000h 4 r 05h last tx confirm 0000000000h 5 r 06h phy_data 00000000000000000000h 10 r/e 07h dl_data 0000000000000000h 8 r/e 08h ss_data 00000000000000000000h 10 r/e 09h host interface timeout c8280ah 3 r/w 0ah firmware version 00420097h 4 r
docid17385 rev 3 35/43 UM0932 management information base (mib) 43 4.2 mib parameters in this section all the mib ob ject is described in detail. 4.2.1 00h (modem configuration) this object stores the setting used to functi onally configure the modem. it can be read or written. 4.2.2 01h (phy la yer configuration) this object stores the settings used to configure the modem at physical layer. it can be read or written. table 53. mib object 00h: mib_writerequest and mib_readrequest data format byte index bit index label description and available values factory default value 0 0 ? 1 access mode active layer for received frames 0: phy layer 1: dl layer 2: ss layer 1 (dl layer) 2 sniffer mode sniffer feature on received frames (active on dl and ss layer only) 0: not active 1: active 0 (not active) 3 - 4 crc length crc length on dl frames 0: 1 byte (crc-8) 1: 2 byte (crc-16), big endian 2: 4 byte (crc-32), little endian 3: 4 byte (crc-32), big endian 2 5 reserved always equal to 0 0 6 dl crc on phy length fields of dl frame ( figure 3 ) involved in crc calculation active on handled dl and ss frames only) 0: crc calculated over dl payload only 1: crc calculated over dl payload and phy length 0 7 unused unused value 0 table 54. mib object 01h: mib_writerequest and mib_readrequest data format byte index bit index label description and available values factory default value 0 ? 2 high frequency high frequency used for communication [hz]. any value in cenelec band a, b, c, d. 86000 (014ff0h) 3 ? 5 low frequency low frequency used for communication [hz]. any value in cenelec band a, b, c, d. 72000 (011940h)
management information base (mib) UM0932 36/43 docid17385 rev 3 6 0 rx mode active channels for reception 0: high channel only 1: dual channel 0 (high channel) 1 rx high channel modulation functional modulation on high channel 0: fsk 1: all allowed psk modulations 1 (psk) 2 rx low channel modulation functional modulation on low channel (ignored if rx mode is high channel only) 0: fsk 1: all allowed psk modulations 1 (psk) 3 current control tx current limiting enable flag 0: disabled 1: enabled 1 (enabled) 4 - 7 unused unused bits 0 7 0 - 4 tx gain default tx gain value to be used in transmission (when gain selector parameter in any datarequest- see table 35 , is equal to 0) 15h (21) 5 - 7 reserved reserved bits 0 8 - 9 zc delay if zc delay parameter in any datarequest is equal to 1 ( table 35 ), delay set during transmission between the outgoing frame start and the mains zero-crossing (signed value), expressed in 13 s step 0 10 0 - 1 psk preamble length preamble length for psk communication. 0: 16 bit 1: 24 bit 2: 32 bit 3: 40 bit 2 (32 bit) 2 - 7 unused unused bits 0 table 54. mib object 01h: mib_writerequest and mib_readrequest data format (continued) byte index bit index label description and available values factory default value
docid17385 rev 3 37/43 UM0932 management information base (mib) 43 4.2.3 02h (ss key) this object holds the key used by the ss su b-system to encrypt and decrypt transmitted and received data. it can be read or written. 4.2.4 04h (last data indication) this object stores inform ation about the last indication message received (among phy_dataindication section 3.3.14 , dl_dataindication section 3.3.17 , ss_dataindication section 3.3.21 , dl_snifferindication section 3.3.17 , ss_snifferindication section 3.3.22 ). its field values are equal to those notified by the last indication message and presented in the four first bytes (0 ? 3) of the indicationdata ( table 39 , 48 ). it can be read only. 11 0 - 1 fsk bit rate bit rate for fsk communication. 0: 1200 bps 1: 2400 bps 2: 4800 bps 3: 9600 bps 1 (2400 bps) 2 fsk deviation deviation for fsk communication. 0: 0.5 1: 1 1 3 ? 4 fsk preamble length preamble length for fsk communication. 0: 16 bit 1: 24 bit 2: 32 bit 3: 40 bit 2 (32 bit) 5 fsk unique word length unique word length for fsk communication. 0: 8 bit 1: 16 bit 1 (16 bit) 6 reserved reserved bit 0 7 ? 8 unused unused bits 0 12 fsk unique word msbyte fsk modulation unique word msb (used if unique word length is 16 bits only) 9bh 13 fsk unique word lsbyte fsk modulation unique word lsb 58h table 54. mib object 01h: mib_writerequest and mib_readrequest data format (continued) byte index bit index label description and available values factory default value table 55. mib object 02h: mib_writerequest and mib_readrequest data format byte index label description and available values factory default value 0 ? 15 ss key 128-bit aes key used to process transmitted and received frames. 00000000000000000000000000000000
management information base (mib) UM0932 38/43 docid17385 rev 3 4.2.5 05h (last tx confirm) this object stores inform ation about last confirm message received (among phy_dataconfirm section 3.3.13 , dl_dataconfirm section 3.3.16 , ss_dataconfirm section 3.3.20 ). its field values are equal to those notified by last confirm message and presented in the first five bytes (0 ? 2) of the confirmdata ( table 37 ). it can be read only. table 56. mib object 04h: mib_writerequest and mib_readrequest data format byte index bit index label description and available values factory default value 0 0 ? 2 frame modulation frame modulation on the last indication received (data/sniffer, phy, dl, ss) 0: b-psk 1: q-psk 2: 8-psk 3: b-fsk 4: b-psk coded 5: q-psk coded 6: reserved 7: b-psk coded with peak noise avoidance 0 3 rx channel rx channel on the last indication received 0: low channel 1: high channel 0 4 ? 7 pga value pga value on the last indication received 0 1snr snr estimated over the unique wo rd reception (signed value, valid for psk received frames only, equal to 255 ? no meaning ? for fsk received frames) 00h 2 ? 3 zc delay delay between the received uw last bit and the mains zero- crossing (signed value), expressed in 13 s step 0000h
docid17385 rev 3 39/43 UM0932 management information base (mib) 43 table 57. mib object 05h: mib_writerequest and mib_readrequest data format byte index bit index label description factory default value 0 0 ? 1 max. temp. max. temperature reached during phy frame transmission. 0: t < 70 c (typical) 1: 70 c < t < 100 c (typical) 2: 100 c < t < 125 c (typical) 3: t > 125 c (typical) 0 2 ? 6 max. gain if current control feature (m ib object phy config 01h, table 54 ) is active, max. gain used during the last transmission. if current control feature is not active, gain used during last transmission. 0 7 unused 0 1 0 ? 1 min. temp min. temperature reached during phy frame transmission. 0: t < 70 c (typical) 1: 70 c < t < 100 c (typical) 2: 100 c < t < 125 c (typical) 3: t > 125 c (typical) 0 2 ? 6 min. gain if current control feature (mib object phy config 01h, table 54 ) is active, min. gain used during last transmission. if current control feature is not active, gain used during last transmission. 0 7 unused 0 2 0 ? 6 overcurrent events number number of overcurrent events reached during phy frame transmission. valid if the current control feature is active only. 0 7 overcurrent notification notification about the over current reached during last transmission. valid whether the current control is active or not. 0: max. output current [ ] value not reached 1: max. output current [ ] value reached 0 3 - 4 zc delay delay between the last transmitted uw last bit and the mains zero-crossing (signed value), expressed in 13 s step 0
management information base (mib) UM0932 40/43 docid17385 rev 3 4.2.6 06h (phy data) this object stores counters of power line fram es transmitted or received by the st7580 in compliance with physical frame features. it can be read or erased only. 4.2.7 07h (dl data) this object stores counters of power line fram es transmitted or received by the st7580 in compliance with data link frame features. it can be read or erased only. table 58. mib object 06h: mib_writerequest and mib_readrequest data format byte index label description factory default value 0 ? 1 received unique word counter counter of preamble and unique word sequences received 0000h 2 - 3 phy valid received frames counter counter of valid received phy frame (right preamble, uw). if the modem is set at dl or ss layer (through mib object modem configuration 00h, section 4.2.1 ), it includes any wrong and malformed frames (crc wrong, invalid key) also. unsigned value. 0000h 4 - 5 phy transmitted frames counter counter of valid tran smitted phy frames (phy_dataconfirm number). unsigned value. 0000h 6 ? 7 phy refused transmission counter counter of refused transmissions on phy frames (phy_dataerror number). unsigned value. 0000h 8 - 9 network period mains period, expressed in 13 s step, updated during last reception or transmission 0000h table 59. mib object 07h: mib_writerequest and mib_readrequest data format byte index label description factory default value 0 ? 1 dl valid received frames counter counter of valid received dl frames (right crc). if the modem is set the ss layer (through mib object modem configuration 00h, section 4.2.1 ), it includes any ss wrong and malformed frames (invalid key) as well. unsigned value. 0000h 2 - 3 dl invalid received frames counter counter of invalid received dl frames (wrong crc). unsigned value. 0000h 4 - 5 dl transmitted frames counter counter of valid transmitted dl frames (dl_dataconfirm number). unsigned value. 0000h 6 ? 7 dl refused transmission counter counter of refused transmissions on dl frames (dl_dataerror number). unsigned value. 0000h
docid17385 rev 3 41/43 UM0932 management information base (mib) 43 4.2.8 08h (ss data) this object stores counters of power line fram es transmitted or received by the st7580 in compliance with data link frame features. it can be read or erased only. 4.2.9 09h (host interface timeout) this object stores the host interface timeout values that the st7580 can handle ( table 6 ). it can be read or written. 4.2.10 0ah (firmware version) this object stores the embedded firmware ve rsion (st internal reference). it can be read only. table 60. mib object 08h: mib_writerequest and mib_readrequest data format byte index label description factory default value 0 ? 1 ss valid received frames counter counter of valid received ss frames (ss_dataindication number). unsigned value. 0000h 2 ? 3 ss not authentic received frames counter counter of not authentic received ss frames (wrong digest). unsigned value. 0000h 4 ? 5 ss malformed received frames counter of malformed received ss frames (wrong length). unsigned value. 0000h 6 ? 7 ss transmitted frames counter counter of valid transmitted ss frames (ss_dataconfirm number). unsigned value. 0000h 8 - 9 ss refused transmission counter counter of refused transmissions on ss frames (ss_dataerror number). unsigned value. 0000h table 61. mib object 09h: mib_writerequest and mib_readrequest data format byte index label description and available values factory default value 0t sr t sr timeout value [ms] 200 (c8h) 1t ack t ack timeout value [ms] 40 (28h) 2t ic t ic timeout value [ms] 10 (0ah) table 62. mib object 0ah: mib_writerequest and mib_readrequest data format byte index label description and a vailable values factor y default value 0 - 3 fw version fw release number (st internal reference) 00420097h
reference UM0932 42/43 docid17385 rev 3 5 reference ? stmicroelectronics, st7580 datasheet. 6 revision history table 63. document revision history date revision changes 04-nov-2011 1 initial release 23-oct-2012 2 ? corrected parameter (length fields) at ta ble 6 , 35 , 39 and 52 ? added parameters values on table 45 02-oct-2013 3 ? updated ta ble 8 and ta ble 19 . ? minor modifications throughout document.
docid17385 rev 3 43/43 UM0932 43 please read carefully: information in this document is provided solely in connection with st products. stmicroelectronics nv and its subsidiaries (?st ?) reserve the right to make changes, corrections, modifications or improvements, to this document, and the products and services described he rein at any time, without notice. all st products are sold pursuant to st?s terms and conditions of sale. purchasers are solely responsible for the choice, selection and use of the st products and services described herein, and st as sumes no liability whatsoever relating to the choice, selection or use of the st products and services described herein. no license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted under this document. i f any part of this document refers to any third party products or services it shall not be deemed a license grant by st for the use of such third party products or services, or any intellectual property contained therein or considered as a warranty covering the use in any manner whatsoev er of such third party products or services or any intellectual property contained therein. unless otherwise set forth in st?s terms and conditions of sale st disclaims any express or implied warranty with respect to the use and/or sale of st products including without limitation implied warranties of merchantability, fitness for a parti cular purpose (and their equivalents under the laws of any jurisdiction), or infringement of any patent, copyright or other intellectual property right. st products are not designed or authorized for use in: (a) safety critical applications such as life supporting, active implanted devices or systems wi th product functional safety requirements; (b) aeronautic applications; (c) automotive applications or environments, and/or (d) aerospace applications or environments. where st products are not designed for such use, the purchaser shall use products at purchaser?s sole risk, even if st has been informed in writing of such usage, unless a product is expressly designated by st as being intended for ?automotive, automotive safety or medical? industry domains according to st product design specifications. products formally escc, qml or jan qualified are deemed suitable for use in aerospace by the corresponding governmental agency. resale of st products with provisions different from the statements and/or technical features set forth in this document shall immediately void any warranty granted by st for the st product or service described herein and shall not create or extend in any manner whatsoev er, any liability of st. st and the st logo are trademarks or registered trademarks of st in various countries. information in this document supersedes and replaces all information previously supplied. the st logo is a registered trademark of stmicroelectronics. all other names are the property of their respective owners. ? 2013 stmicroelectronics - all rights reserved stmicroelectronics group of companies australia - belgium - brazil - canada - china - czech republic - finland - france - germany - hong kong - india - israel - ital y - japan - malaysia - malta - morocco - philippines - singapore - spain - sweden - switzerland - united kingdom - united states of america www.st.com

▲Up To Search▲

Price & Availability of UM0932

	To Download UM0932 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .